home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
SGI Freeware 2002 November
/
SGI Freeware 2002 November - Disc 2.iso
/
dist
/
fw_hylafax.idb
/
usr
/
freeware
/
catman
/
u_man
/
cat1
/
faxcover.Z
/
faxcover
Wrap
Text File
|
2002-07-08
|
11KB
|
206 lines
FAXCOVER(1) FAXCOVER(1)
NNAAMMEE
faxcover - generate a POSTSCRIPT cover page for an outgo
ing facsimile
SSYYNNOOPPSSIISS
ffaaxxccoovveerr [ _o_p_t_i_o_n_s ] --ff _f_r_o_m_-_n_a_m_e --nn _f_a_x_-_n_u_m_b_e_r
DDEESSCCRRIIPPTTIIOONN
_f_a_x_c_o_v_e_r generates a POSTSCRIPT cover page document on
the standard output. The cover page fills the entire area
of a default page and is created according to the informa
tion supplied on the command line and a _c_o_v_e_r _s_h_e_e_t _t_e_m_
_p_l_a_t_e file.
_f_a_x_c_o_v_e_r is normally invoked by the _s_e_n_d_f_a_x(1) program to
generate a cover page for each outgoing facsmile.
_f_a_x_c_o_v_e_r works by creating a POSTSCRIPT dictionary that
contains definitions for the variable information that is
to be placed on the facsimile cover page. Specifically, a
dictionary with the following symbols are defined:
SSyymmbbooll DDeessccrriippttiioonn SSyymmbbooll DDeessccrriippttiioonn
_t_o destination person _f_r_o_m _s_e_n_d_i_n_g person
_t_o_-_c_o_m_p_a_n_y destination company _f_r_o_m_-_c_o_m_p_a_n_y sender's company
_t_o_-_l_o_c_a_t_i_o_n destination geographic location _f_r_o_m_-_l_o_c_a_t_i_o_n sender geographic location
_t_o_-_v_o_i_c_e_-_n_u_m_b_e_r person's voice phone number _f_r_o_m_-_v_o_i_c_e_-_n_u_m_b_e_r sender's voice phone number
_t_o_-_f_a_x_-_n_u_m_b_e_r destination fax phone number _f_r_o_m_-_f_a_x_-_n_u_m_b_e_r sender's fax phone number
_c_o_m_m_e_n_t_s unbroken comment string _c_o_m_m_e_n_t_s_X _X'th line of comments
_r_e_g_a_r_d_i_n_g Re: subject _C_o_m_m_e_n_t_X similar to _c_o_m_m_e_n_t_s_X
_p_a_g_e_W_i_d_t_h page width in millimeters _p_a_g_e_-_c_o_u_n_t # pages other than cover page
_p_a_g_e_L_e_n_g_t_h page length in millimeters _t_o_d_a_y_s_-_d_a_t_e current date and time
If the _c_o_m_m_e_n_t_s string is longer than _m_a_x_l_e_n_c_o_m_m_e_n_t_s char
acters, it is broken, on word boundaries or instances of
``\n, into multiple POSTSCRIPT strings _c_o_m_m_e_n_t_s_X where _X
is the line number; e.g. _c_o_m_m_e_n_t_s_2 for the second line of
comments. Long substrings without whitespace which exceed
_m_a_x_l_e_n_c_o_m_m_e_n_t_s are also broken. By default _f_a_x_c_o_v_e_r will
generate 20 _c_o_m_m_e_n_t_s_X strings, emitting null string values
for empty lines. This number can be changed with the --mm
option; see below. _m_a_x_l_e_n_c_o_m_m_e_n_t_s is changed with the --zz
option; see below.
Note that use of _c_o_m_m_e_n_t_s_X with non-fixed-width fonts can
lead to spatial problems where characters run off the edge
of the generated cover page. In such cases, use of _B_r_e_a_k_
_I_n_t_o_L_i_n_e_s (see below) may be a more suitable approach.
_C_o_m_m_e_n_t_X is similar to _c_o_m_m_e_n_t_s_X except that its values
are created only by breaking _c_o_m_m_e_n_t_s on instances of
``\n and not otherwise. _m_a_x_l_i_n_e_s does not affect _C_o_m_
_m_e_n_t_X
_f_a_x_c_o_v_e_r also emits a POSTSCRIPT procedure for breaking
comment strings into multiple lines using the POSTSCRIPT
font metric information. This procedure is named _B_r_e_a_k_I_n_
_t_o_L_i_n_e_s and has the following usage convention:
%<line-width> <line-height> <x> <y> <string> BreakInto
Lines -
eg
/rule (_____________________________________________) def
/lw rule stringwidth pop def /lh 30 def
/y 191.4 def /x 0 def
y -30 0 { x exch moveto rule show } for
lw lh x y comments BreakIntoLines
where the width of the rule controls the length of each
line of comments (note that it is made slightly shorter
here for the purpose of presentation), _x and _y are ini
tialized to coordinate locations on the page where the
comment string should be imaged, and the number 30 is the
inter-line spacing appropriate for the font used to image
the comment lines.
If information is unavailable for an item, the associated
POSTSCRIPT symbol is defined to be a null string.
Following the definition prologue, a cover sheet template
file is copied. This file is expected to be a POSTSCRIPT
program that uses the generated strings to create a cover
page. The template must include a sshhoowwppaaggee operator to
cause the page to be imaged. The above symbols will be
defined in the _c_u_r_r_e_n_t _d_i_c_t_i_o_n_a_r_y. A trailing eenndd opera
tor is supplied by _f_a_x_c_o_v_e_r, so any manipulation of the
dictionary stack should leave the current dictionary on
the top of the stack on completion.
OOPPTTIIOONNSS
--cc _c_o_m_m_e_n_t_s Use _c_o_m_m_e_n_t_s for the comment string. You may
use '\n' to break it into several lines on
generated the cover page.
--CC _f_i_l_e Use _f_i_l_e as the template file. The default
template file is named _f_a_x_c_o_v_e_r_._p_s. The tem
plate file can also be specified by setting
the FAXCOVER environment variable. If the
template filename is not an absolute pathname,
then _f_a_x_c_o_v_e_r looks first for this file in the
home directory of the sender. If no such file
is present, then it looks in the library
directory where the _H_y_l_a_F_A_X client application
data are installed. If no template file is
located, _f_a_x_c_o_v_e_r will terminate without gen
erating a cover page.
--DD _f_o_r_m_a_t Use _f_o_r_m_a_t as the formatting specification
passed to _s_t_r_f_t_i_m_e(3) when generating the time
and date placed on the cover page.
--ff _n_a_m_e Use _n_a_m_e for the sender's identity.
--ll _l_o_c_a_t_i_o_n Use _l_o_c_a_t_i_o_n for the geographic location of
the destination company.
--LL _l_o_c_a_t_i_o_n Use _l_o_c_a_t_i_o_n for the geographic location of
the sender's company.
--mm _m_a_x_l_i_n_e_s indicates the maximum number of _c_o_m_m_e_n_t_s_X
lines to generate.
--nn _n_u_m_b_e_r Use _n_u_m_b_e_r for the destination fax machine
number.
--NN _n_u_m_b_e_r Use _n_u_m_b_e_r for the sender's fax machine num
ber.
--pp _c_o_u_n_t Use _c_o_u_n_t for the count of pages to follow the
cover page.
--rr _r_e_g_a_r_d_i_n_g
Use _r_e_g_a_r_d_i_n_g for the ``Re:'' field.
--ss _s_i_z_e Set the page size to use for the transmitted
facsimile. Facsimile are normally imaged with
a system-default page size (usually letter-
size pages, 8.5" by 11", for sites in North
America). Alternate page sizes are specified
symbolically using either the name or abbrevi
ation of an entry in the _p_a_g_e_s_i_z_e_s(${MAN
NUM4_5}) database; e.g. _a_3 (ISO A3), _a_4 (ISO
A4), _a_5 (ISO A5), _a_6 (ISO A6), _b_4 (ISO B4),
_n_a_-_l_e_t (North American Letter), _u_s_-_l_e_g (Ameri
can Legal), _u_s_-_l_e_d (American Ledger), _u_s_-_e_x_e
(American Executive), _j_p_-_l_e_t (Japanese Let
ter), and _j_p_-_l_e_g (Japanese Legal). Compar
isons are case-insensitive and any match of a
substring of the full page-size name is suffi
cient; e.g. ``legal'' would match ``American
Legal''.
Note that it may not be permissible to image
into the full page area; the guaranteed repro
ducible area for a page is typically inset.
Also, note that while arbitrary page sizes can
be specified through the page size database,
only a limited set of page dimensions are sup
ported by the Group 3 facsimile protocol.
Thus if an odd-size facsimile is submitted for
transmission it may not be possible to deter
mine if it can be sent until the fax server
establishes communication with the remote fac
simile machine.
--tt _n_a_m_e Use _n_a_m_e for the receiver's identity.
--vv _n_u_m_b_e_r Use _n_u_m_b_e_r for the receiver's voice phone num
ber.
--VV _n_u_m_b_e_r Use _n_u_m_b_e_r for the sender's voice phone num
ber.
--xx _c_o_m_p_a_n_y Use _c_o_m_p_a_n_y for the destination company name.
--XX _c_o_m_p_a_n_y Use _c_o_m_p_a_n_y for the sender's company name.
--zz _m_a_x_l_e_n_c_o_m_m_e_n_t_s
indicates the maximum length in number of
characters allowed in a _c_o_m_m_e_n_t_s_X string.
DDIIAAGGNNOOSSTTIICCSS
Complaints about not being able to locate a template file.
FFIILLEESS
~/.faxdb personal fax number database
~/.hylarc per-user configuration file
${LIBDATA}/hyla.conf system-wide configuration file
${LIBDATA}/faxcover.ps default cover page template
${LIBDATA}/pagesizes page size database
BBUUGGSS
_f_a_x_c_o_v_e_r should be able to determine the appropriate
length of _c_o_m_m_e_n_t_s_X strings by using font metric informa
tion.
SSEEEE AALLSSOO
_h_y_l_a_f_a_x_-_c_l_i_e_n_t(1), _s_e_n_d_f_a_x(1)
January 06, 2001 FAXCOVER(1)